System for extracting header labels for header cells in tables having complex header structures

ABSTRACT

A method, system and computer-usable medium are disclosed for associating data cells with headers and header labels. In certain embodiments, a table having rows and columns is received, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information. A determination is made as to whether a cell is a header cell or data cell. If the cell is a header cell, current list of column and current list of row headers are dynamically updated. The current list of column and row headers are assigned to the cell regardless of whether the cell is a header cell or data cell. Headers associated with header cells are used to identify label candidates for the header name of the header cell. The labels may be used to provide additional context for headers within a data cell.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates in general to the field of computers and similar technologies, and in particular to software utilized in this field. Still more particularly, it relates to a method, system and computer-usable medium for extracting header labels for header cells in tables having complex header structures to provide enhanced context for table data.

Description of the Related Art

With the increased usage of computing networks, such as the Internet, humans are currently inundated and overwhelmed with the amount of information available to them from various structured and unstructured sources. However, information gaps abound as users try to piece together what they can find that they believe to be relevant during searches for information on various subjects. To assist with such searches, recent research has been directed to generating knowledge management systems which may take an input, analyze it, and return results indicative of the most probable results to the input. Knowledge management systems provide automated mechanisms for searching through a knowledge base with numerous sources of content, e.g., electronic documents, and analyze them with regard to an input to determine a result and a confidence measure as to how accurate the result is in relation to the input.

One such knowledge management system is the IBM Watson™ system available from International Business Machines (IBM) Corporation of Armonk, N.Y. The IBM Watson™ system is an application of advanced natural language processing, information retrieval, knowledge representation and reasoning, and machine learning technologies to the field of open domain question answering. The IBM Watson™ system is built on IBM's DeepQA technology used for hypothesis generation, massive evidence gathering, analysis, and scoring. DeepQA takes an input question, analyzes it, decomposes the question into constituent parts, generates one or more hypothesis based on the decomposed question and results of a primary search of answer sources, performs hypothesis and evidence scoring based on a retrieval of evidence from evidence sources, performs synthesis of the one or more hypothesis, and based on trained models, performs a final merging and ranking to output an answer to the input question along with a confidence measure.

SUMMARY OF THE INVENTION

A method, system and computer-usable medium are disclosed for associating data cells with headers and header labels. In certain embodiments, the method comprises: receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, dynamically updating a current list of column headers; dynamically updating a current list of row headers; dynamically updating a list of header names for the header cell using the current list of column headers and current list of row headers; upon encountering a data cell, assigning the current list of column and row headers to the data cell; and identifying label candidates for the header cell from the list of header names; and assigning one or more label candidates as labels to the header cell.

Certain embodiments relate to a system comprising: a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, dynamically updating a current list of column headers; dynamically updating a current list of row headers; dynamically updating a list of header names for the header cell using the current list of column headers and current list of row headers; upon encountering a data cell, assigning the current list of column and row headers to the data cell; and identifying label candidates for the header cell from the list of header names; and assigning one or more label candidates as labels to the header cell

Certain embodiments relate to a non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, dynamically updating a current list of column headers; and dynamically updating a list of header names for the header cell using the current list of column headers and current list of row headers; upon encountering a data cell, assigning the current list of column and row headers to the data cell; and identifying label candidates for the header cell from the list of header names; and assigning one or more label candidates as labels to the header cell

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.

FIG. 1 shows a schematic diagram of one illustrative embodiment of a question/answer (QA) system.

FIG. 2 shows a simplified block diagram of an information processing system capable of performing computing operations.

FIG. 3 depicts one example of tabular information that may be used to provide an understanding of certain embodiments of a header label assignment system.

FIG. 4 is a flowchart depicting exemplary operations that may be executed in certain embodiments of the header label assignment system.

FIG. 5 is another flowchart depicting exemplary operations that may be executed in certain embodiments of the header label assignment system.

FIG. 6 is a flowchart depicting exemplary operations that may be executed when a determination is made that the cell at the indexed row and indexed column is a data cell.

FIG. 7 is a flowchart depicting exemplary operations that may be executed to identify label candidates using header cell objects.

FIG. 8 shows one example of a data structure that may be generated from the table information shown in FIG. 3 using certain embodiments of the header label assignment system.

FIG. 9 shows another example of a table 900 including information from which header labels may be extracted to enhance the context of the data cells.

FIG. 10 depicts one example of pseudocode that may be used as a basis to implement certain embodiments of the header label assignment system.

DETAILED DESCRIPTION

The present invention may be a system, a method, and/or a computer program product. In addition, selected aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and/or hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of computer program product embodied in a computer-readable storage medium, or media, having computer-readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a dynamic or static random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a magnetic storage device, a portable Compact Disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer-readable program instructions described herein can be downloaded to respective computing/processing devices from a computer-readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a Public Switched Circuit Network (PSTN), a packet-based network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a wireless network, or any suitable combination thereof. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing/processing device.

Computer-readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language, Hypertext Precursor (PHP), or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server or cluster of servers. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a LAN or a WAN, or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a sub-system, module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

FIG. 1 shows a schematic diagram of one illustrative embodiment of a QA system 100 and a question prioritization system 110 connected to a computer network 140 to operate as a conversational system. The QA system 100 includes a knowledge manager 104 that is connected to a knowledge base 106 and configured to provide QA generation functionality for one or more content creators and/or users 130 who submit content across the network 140 to the QA system 100. To assist with efficient sorting and presentation of questions to the QA system 100, the question prioritization system 110 may be connected to the computer network 140 to receive user questions, and may include a plurality of sub-systems which interact with cognitive systems, like the QA system 100, to prioritize questions or requests being submitted to the QA system 100.

The Named Entity sub-system 112 receives and processes each question 111 by using natural language processing (NLP) to analyze each question and extract question topic information contained in the question, such as named entities, phrases, urgent terms, and/or other specified terms which are stored in one or more domain entity dictionaries 113. By leveraging a plurality of pluggable domain dictionaries 113 relating to different domains or areas (e.g., travel, healthcare, electronics, game shows, financial services, etc.), the domain dictionary 113 enables critical and urgent words (e.g., “threat level”) from different domains (e.g., “travel”) to be identified in each question based on their presence in the domain dictionary 113. To this end, the Named Entity sub-system 112 may use an NLP routine to identify the question topic information in each question. As used herein, “NLP” broadly refers to the field of computer science, artificial intelligence, and linguistics concerned with the interactions between computers and human (natural) languages. In this context, NLP is related to the area of human-computer interaction and Natural Language understanding by computer systems that enable computer systems to derive meaning from human or Natural Language input. For example, NLP can be used to derive meaning from a human-oriented question such as, “What is tallest mountain in North America?” and to identify specified terms, such as named entities, phrases, or urgent terms contained in the question. The process identifies key terms and attributes in the question and compares the identified terms to the stored terms in the domain dictionary 113.

The Question Priority Manager sub-system 114 performs additional processing on each question to extract question context information 115A. In addition, or in the alternative, the Question Priority Manager sub-system 114 may also extract server performance information 115B for the question prioritization system 110 and/or QA system 100. In selected embodiments, the extracted question context information 115A may include data that identifies the user context and location when the question was submitted or received. For example, the extracted question context information 115A may include data that identifies the user who submitted the question (e.g., through login credentials), the device or computer which sent the question, the channel over which the question was submitted, or any combination thereof. Other examples may include the location of the user or device that sent the question, any special interest location indicator (e.g., hospital, public-safety answering point, etc.), other context-related data for the question, or any combination thereof. In certain embodiments, the location information is determined through the use of a Geographical Positioning System (GPS) satellite 168. In these embodiments, a handheld computer or mobile telephone 150, or other device, uses signals transmitted by the GPS satellite 168 to generate location information, which in turn is provided via the computer network 140 to the Question Priority Manager sub-system 114 for processing.

In various embodiments, the source for the extracted context information 115A may be a data source 166 accessed through the computer network 140. Examples of a data source 166 include systems that provide telemetry information, such as medical information collected from medical equipment used to monitor a patient's health, environment information collected from a facilities management system, or traffic flow information collected from a transportation monitoring system. In certain embodiments, the data source 166 may be a storage area network (SAN) or other network-based repositories of data.

In various embodiments, the data source 166 may provide data directly or indirectly collected from “big data” sources. In general, big data refers to a collection of datasets so large and complex that traditional database management tools and data processing approaches are inadequate. These datasets can originate from a wide variety of sources, including computer systems (e.g., 156, 158, 162), mobile devices (e.g., 150, 152, 154), financial transactions, streaming media, social media, as well as systems (e.g., 166) commonly associated with a wide variety of facilities and infrastructure (e.g., buildings, factories, transportation systems, power grids, pipelines, etc.). Big data, which is typically a combination of structured, unstructured, and semi-structured data poses multiple challenges, including its capture, curation, storage, transfer, search, querying, sharing, analysis and visualization.

The Question Priority Manager sub-system 114 may also determine or extract selected server performance data 115B for the processing of each question. In certain embodiments, the server performance information 115B may include operational metric data relating to the available processing resources at the question prioritization system 110 and/or QA system 100, such as operational or run-time data, CPU utilization data, available disk space data, bandwidth utilization data, and so forth. As part of the extracted information 115A/B, the Question Priority Manager sub-system 114 may identify the Service Level Agreement (SLA) or Quality of Service (QoS) processing requirements that apply to the question being analyzed, the history of analysis and feedback for the question or submitting user, and the like. Using the question topic information and extracted question context 115A and/or server performance information 115B, the Question Priority Manager sub-system 114 is configured to populate feature values for the Priority Assignment Model 116. In various embodiments, the Priority Assignment Model 116 provides a machine learning predictive model for generating target priority values for the question, such as by using an artificial intelligence (AI) approaches known to those of skill in the art. In certain embodiments, the AI logic is used to determine and assign a question urgency value to each question for purposes of prioritizing the response processing of each question by the QA system 100.

The Prioritization Manager sub-system 117 performs additional sort or rank processing to organize the received questions based on at least the associated target priority values such that high priority questions are put to the front of a prioritized question queue 118 for output as prioritized questions 119. In the question queue 118 of the Prioritization Manager sub-system 117, the highest priority question is placed at the front of the queue for delivery to the assigned QA system 100. In selected embodiments, the prioritized questions 119 from the Prioritization Manager sub-system 117 that have a specified target priority value may be assigned to a particular pipeline (e.g., QA system pipeline 100A, 100B) in the QA system 100. As will be appreciated, the Prioritization Manager sub-system 117 may use the question queue 118 as a message queue to provide an asynchronous communications protocol for delivering prioritized questions 119 to the QA system 100. Consequently, the Prioritization Manager sub-system 117 and QA system 100 do not need to interact with a question queue 118 at the same time by storing prioritized questions in the question queue 118 until the QA system 100 retrieves them. In this way, a wider asynchronous network supports the passing of prioritized questions 119 as messages between different QA system pipelines 100A, 100B, connecting multiple applications and multiple operating systems. Messages can also be passed from queue to queue in order for a message to reach the ultimate desired recipient. An example of a commercial implementation of such messaging software is IBM's WebSphere MQ (previously MQ Series). In selected embodiments, the organizational function of the Prioritization Manager sub-system 117 may be configured to convert over-subscribing questions into asynchronous responses, even if they were asked in a synchronized fashion.

The QA system 100 may include one or more QA system pipelines 100A, 100B, each of which includes a computing device 104 comprising one or more processors and one or more memories. The QA system pipelines 100A, 100B may likewise include potentially any other computing device elements generally known in the art including buses, storage devices, communication interfaces, and the like. In various embodiments, these computing device elements may be implemented to process questions received over the network 140 from one or more content creator and/or users 130 at computing devices (e.g., 150, 152, 154, 156, 158, 162). In certain embodiments, the one or more content creator and/or users 130 are connected over the network 140 for communication with each other and with other devices or components via one or more wired and/or wireless data communication links, where each communication link may comprise one or more of wires, routers, switches, transmitters, receivers, or the like. In this networked arrangement, the QA system 100 and network 140 may enable QA generation functionality for one or more content users 130. Other embodiments of QA system 100 may be used with components, systems, sub-systems, and/or devices other than those that are depicted herein.

In each QA system pipeline 100A, 100B, a prioritized question 119 is received and prioritized for processing to generate an answer 120. In sequence, prioritized questions 119 are de-queued from the shared question queue 118, from which they are de-queued by the pipeline instances for processing in priority order rather than insertion order. In selected embodiments, the question queue 118 may be implemented based on a “priority heap” data structure. During processing within a QA system pipeline (e.g., 100A, 100B), questions may be split into multiple subtasks, which run concurrently. In various embodiments, a single pipeline instance may process a number of questions concurrently, but only a certain number of subtasks. In addition, each QA system pipeline 100A, 100B may include a prioritized queue (not shown) to manage the processing order of these subtasks, with the top-level priority corresponding to the time that the corresponding question started (i.e., earliest has highest priority). However, it will be appreciated that such internal prioritization within each QA system pipeline 100A, 100B may be augmented by the external target priority values generated for each question by the Question Priority Manager sub-system 114 to take precedence, or ranking priority, over the question start time. In this way, more important or higher priority questions can “fast track” through a QA system pipeline 100A, 100B if it is busy with already-running questions.

In the QA system 100, the knowledge manager 104 may be configured to receive inputs from various sources. For example, knowledge manager 104 may receive input from the question prioritization system 110, network 140, a knowledge base or corpus of electronic documents 107 or other data, semantic data 108, content creators, and/or users 130, and other possible sources of input. In selected embodiments, some or all of the inputs to knowledge manager 104 may be routed through the network 140 and/or the question prioritization system 110. The various computing devices (e.g., 150, 152, 154, 156, 158, 162) on the network 140 may include access points for content creators and/or users 130. Some of the computing devices may include devices for a database storing a corpus of data as the body of information used by the knowledge manager 104 to generate answers to cases. The network 140 may include local network connections and remote connections in various embodiments, such that knowledge manager 104 may operate in environments of any size, including local (e.g., a LAN) and global (e.g., the Internet). Additionally, knowledge manager 104 serves as a front-end system that can make available a variety of knowledge extracted from or represented in documents, network-accessible sources and/or structured data sources. In this manner, some processes populate the knowledge manager, with the knowledge manager also including input interfaces to receive knowledge requests and respond accordingly.

In one embodiment, a content creator 130 creates content (e.g., a document) in a knowledge base 106 for use as part of a corpus of data used in conjunction with knowledge manager 104. In selected embodiments, the knowledge base 106 may include any file, text, article, or source of data (e.g., scholarly articles, dictionary definitions, encyclopedia references, and the like) for use by the knowledge manager 104. Content users 130 may access the knowledge manager 104 via a network connection or an Internet connection to the network 140, and may input questions to the knowledge manager 104 that may be answered by the content in the corpus of data.

As further described below, when a process evaluates a given section of a document for semantic content, the process can use a variety of conventions to query it from the knowledge manager 104. One convention is to send a well-formed question. As used herein, semantic content broadly refers to content based upon the relation between signifiers, such as words, phrases, signs, and symbols, and what they stand for, their denotation, or connotation. In other words, semantic content is content that interprets an expression, such as by using Natural Language (NL) Processing. In one embodiment, the process sends well-formed questions (e.g., Natural Language questions, etc.) to the knowledge manager 104. In various embodiments, the knowledge manager 104 may interpret the question and provide a response to the content user containing one or more answers to the question. In some embodiments, the knowledge manager 104 may provide a response to users in a ranked list of answers.

In some illustrative embodiments, QA system 100 may be the IBM Watson™ QA system available from International Business Machines Corporation of Armonk, N.Y., which is augmented with the mechanisms of the illustrative embodiments described hereafter. The IBM Watson™ knowledge manager system may receive an input question which it then parses to extract the major features of the question, that in turn are then used to formulate queries that are applied to the corpus of data. Based on the application of the queries to the corpus of data, a set of hypotheses, or candidate answers to the input question, are generated by looking across the corpus of data for portions of the corpus of data that have some potential for containing a valuable response to the input question.

The IBM Watson™ QA system then performs deep analysis on the language of the input prioritized question 119 and the language used in each of the portions of the corpus of data found during the application of the queries using a variety of reasoning algorithms. There may be hundreds or even thousands of reasoning algorithms applied, each of which performs different analysis (e.g., comparisons), and generates a score. For example, certain reasoning algorithms may look at the matching of terms and synonyms within the language of the input question and the found portions of the corpus of data. Other reasoning algorithms may look at temporal or spatial features in the language, while yet others may evaluate the source of the portion of the corpus of data and evaluate its veracity.

The scores obtained from the various reasoning algorithms indicate the extent to which the potential response is inferred by the input question based on the specific area of focus of that reasoning algorithm. Each resulting score is then weighted against a statistical model. The statistical model captures how well the reasoning algorithm performed at establishing the inference between two similar passages for a particular domain during the training period of the IBM Watson™ QA system. The statistical model may then be used to summarize a level of confidence that the IBM Watson™ QA system has regarding the evidence that the potential response, i.e. candidate answer, is inferred by the question. This process may be repeated for each of the candidate answers until the IBM Watson™ QA system identifies candidate answers that surface as being significantly stronger than others and thus, generates a final answer, or ranked set of answers, for the input question. The QA system 100 then generates an output response or answer 120 with the final answer and associated confidence and supporting evidence. More information about the IBM Watson™ QA system may be obtained, for example, from the IBM Corporation website, IBM Redbooks, and the like. For example, information about the IBM Watson™ QA system can be found in Yuan et al., “Watson and Healthcare,” IBM developerWorks, 2011 and “The Era of Cognitive Systems: An Inside Look at IBM Watson and How it Works” by Rob High, IBM Redbooks, 2012.

Types of information processing systems that can utilize QA system 100 range from small handheld devices, such as handheld computer/mobile telephone 150 to large mainframe systems, such as mainframe computer 158. Examples of handheld computer 150 include personal digital assistants (PDAs), personal entertainment devices, such as MP3 players, portable televisions, and Compact Disc players. Other examples of information processing systems include pen, or tablet, computer 152, laptop, or notebook, computer 154, personal computer system 156, server 162, and mainframe computer 158.

As shown, the various information processing systems can be networked together using computer network 140. Types of computer network 140 that can be used to interconnect the various information processing systems include PAN, LANs, Wireless Local Area Networks (WLANs), the Internet, the PSTN, other wireless networks, and any other network topology that can be used to interconnect the information processing systems.

In selected embodiments, the information processing systems include nonvolatile data stores, such as hard drives and/or nonvolatile memory. Some of the information processing systems may use separate nonvolatile data stores. For example, server 162 utilizes nonvolatile data store 164, and mainframe computer 158 utilizes nonvolatile data store 160. The nonvolatile data store can be a component that is external to the various information processing systems or can be internal to one of the information processing systems. An illustrative example of an information processing system showing an exemplary processor and various components commonly accessed by the processor is shown in FIG. 2.

In various embodiments, the QA system 100 is implemented to receive a variety of data from various computing devices (e.g., 150, 152, 154, 156, 158, 162) and data sources 166, which in turn is used to perform QA operations described in greater detail herein. In certain embodiments, the QA system 100 may receive a first set of information from a first computing device (e.g., laptop computer 154). The QA system 100 then uses the first set of data to perform QA processing operations resulting in the generation of a second set of data, which in turn is provided to a second computing device (e.g., server 162). In response, the second computing device may process the second set of data to generate a third set of data, which is then provided back to the QA system 100. In turn, the QA system may perform additional QA processing operations on the third set of data to generate a fourth set of data, which is then provided to the first computing device.

In certain embodiments, a first computing device (e.g., server 162) may receive a first set of data from the QA system 100, which is then processed and provided as a second set of data to another computing device (e.g., mainframe 158). The second set of data is processed by the second computing device to generate a third set of data, which is provided back to the first computing device. The second computing device then processes the third set of data to generate a fourth set of data, which is then provided to the QA system 100, where it is used to perform QA operations described in greater detail herein.

In one embodiment, the QA system may receive a first set of data from a first computing device (e.g., handheld computer/mobile device 150), which is then used to perform QA operations resulting in a second set of data. The second set of data is then provided back to the first computing device, where it is used to generate a third set of data. In turn, the third set of data is provided back to the QA system 100, which then provides it to a second computing device (e.g., mainframe computer 158), where it is used to perform post processing operations.

As an example, a content user 130 may ask the question, “I'm looking for a good pizza restaurant nearby.” In response, the QA system 100 may provide a list of three such restaurants in a half mile radius of the content user. In turn, the content user 130 may then select one of the recommended restaurants and ask for directions, signifying their intent to proceed to the selected restaurant. In this example, the list of recommended restaurants, and the restaurant the content user 130 selected, would be the third set of data provided to the QA system 100. To continue the example, the QA system 100 may then provide the third set of data to the second computing device, where it would be processed to generate a database of the most popular restaurants, by classification, location, and other criteria.

In various embodiments the exchange of data between various computing devices (e.g., 150, 152, 154, 156, 158, 162) results in more efficient processing of data as each of the computing devices can be optimized for the types of data it processes. Likewise, the most appropriate data for a particular purpose can be sourced from the most suitable computing device (e.g., 150, 152, 154, 156, 158, 162), or data source 166, thereby increasing processing efficiency. Skilled practitioners of the art will realize that many such embodiments are possible and that the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 2 illustrates an information processing system 202, more particularly, a processor and common components, which is a simplified example of a computer system capable of performing the computing operations described herein. Information processing system 202 includes a processor unit 204 that is coupled to a system bus 206. A video adapter 208, which controls a display 210, is also coupled to system bus 206. System bus 206 is coupled via a bus bridge 212 to an Input/Output (I/O) bus 214. An I/O interface 216 is coupled to I/O bus 214. The I/O interface 216 affords communication with various I/O devices, including a keyboard 218, a mouse 220, a Compact Disc—Read-Only Memory (CD-ROM) drive 222, a floppy disk drive 224, and a flash drive memory 226. The format of the ports connected to I/O interface 216 may be any known to those skilled in the art of computer architecture, including, but not limited to Universal Serial Bus (USB) ports.

The information processing system 202 is able to communicate with a service provider server 252 via a network 228 using a network interface 230, which is coupled to system bus 206. Network 228 may be an external network such as the Internet, or an internal network such as an Ethernet Network or a Virtual Private Network (VPN). Using network 228, the information processing system 202 is able to access a service provider server 252 to implement the present invention.

A hard drive interface 232 is also coupled to system bus 206. Hard drive interface 232 interfaces with a hard drive 234. In a preferred embodiment, hard drive 234 populates a system memory 236, which is also coupled to system bus 206. Data that populates system memory 236 includes the information processing system's 202 operating system (OS) 238 and software programs 244.

OS 238 includes a shell 240 for providing transparent user access to resources such as software programs 244. Generally, shell 240 is a program that provides an interpreter and an interface between the user and the operating system. More specifically, shell 240 executes commands that are entered into a command line user interface or from a file. Thus, shell 240 (as it is called in UNIX®), also called a command processor in Windows®, is generally the highest level of the operating system software hierarchy and serves as a command interpreter. The shell provides a system prompt, interprets commands entered by keyboard, mouse, or other user input media, and sends the interpreted command(s) to the appropriate lower levels of the operating system (e.g., a kernel 242) for processing. While shell 240 generally is a text-based, line-oriented user interface, the present invention can also support other user interface modes, such as graphical, voice, gestural, etc.

As depicted, OS 238 also includes kernel 242, which includes lower levels of functionality for OS 238, including essential services required by other parts of OS 238 and software programs 244, including memory management, process and task management, disk management, and mouse and keyboard management. In certain embodiments, system memory 236 may also include a Browser 246 having program modules and instructions enabling a World Wide Web (WWW) client (i.e., information processing system 202) to send and receive network messages to the Internet using HyperText Transfer Protocol (HTTP) messaging, thus enabling communication with service provider server 252. In various embodiments, system memory 236 may also include a header label assignment system 248. In various embodiments, header label assignment system 248 includes code for implementing the processes described hereinbelow. In certain embodiments, the information processing system 202 is able to download the header label assignment system 248 from a service provider server 252.

The hardware elements depicted in the information processing system 202 are not intended to be exhaustive, but rather are representative to highlight components that may be used to implement the present invention. For instance, the information processing system 202 may include alternate memory storage devices such as magnetic cassettes, DVDs, Bernoulli cartridges, and the like. These and other variations are intended to be within the spirit, scope and intent of the present invention.

The header label assignment system 248 is designed with an appreciation that tables having data that can be used in an information processing system may include complex header structures. The design and operation of the header label assignment system 248 also appreciates that such complex header structures may limit the ability of QA system 100 to analyze information provided in such tables.

In appreciation of these limitations, certain embodiments of the header label assignment system 248 execute operations that automatically generate data structures that assign headers and header labels within a complex table to corresponding data cells. In certain embodiments, the data structures generated by the header label assignment system 248 may be used in training a QA system so that the QA system is better prepared to analyze and provide answers to natural language questions.

FIG. 3 depicts one example of tabular information that may be used to provide an understanding of certain embodiments of the disclosed system. In this example, the information is arranged as cells in a two-dimensional data structure of rows and columns. In this example, table 305 shows the information in a text file format while table 310 shows the information in a tabular format. The same data is expressed in both tables 305 and 310. For purposes of the following discussion, however, table 310 uses with its implicit column numbers C1-C5 and row numbers R1-R6 to describe positions of cells within the table 310. It will be recognized that the column numbers and row numbers shown in table 310 are provided for indexing purposes and are not necessarily included as cells in either table 305 or 310.

In certain embodiments, each cell of a table is populated with at least one of a header name, data value, or no information. With reference to the example shown in table 310, “header names” are shown in bold type, “data cells” include dollar values, and “no information” is shown as an empty cell place holder. Certain cells also constitute headers for other header cells, which are shown in bold italics. Certain embodiments of the header label assignment system recognize that such headers for other header cells, referenced herein as “labels,” may be used to give additional context to data cells of the table.

Using indices for the relative position of cells within the table 310 as examples, the header name “NYC BOROUGH” is located within the table at indexed locations R1C1 and R2C1. The header name “SPEEDING TICKETS” is located within the table at indexed locations R1C2 and R1C3. The header name “PARKING TICKETS” is located within the table at indexed locations R1C4 and R1C5. The header name “CAR” is located within the table at indexed location R2C2. The data cell “1500” is located within the table at R4C2.

For a computer system to intelligently understand and search data within tables, it needs to correctly identify the headers which apply context to each data cell. In certain embodiments, the data cell “500” may be associated with headers BROOKLYN”, “SUV”, and “SPEEDING TICKETS” as context to the data cell. Certain embodiments of the disclosed system improve the context by additionally labeling the headers. For example, the “BROOKLYN” header can be labeled as a “NYC BOROUGH”. This provides additional value in the data extraction for improved search and answer retrieval. For example, in order to answer the question “What NYC borough had 500 SUV speeding tickets?” from table 310, certain embodiments of the system associate data cell “500” with its row header “BROOKLYN”, and then associate “BROOKLYN” with label “NYC BOROUGH.”

FIG. 4 is a flowchart depicting exemplary operations that may be executed in certain embodiments of the header label assignment system. In certain embodiments, the operations shown in FIG. 4 associate table headers to data cells and can handle more complex tables including nested headers such as those shown in table 310. In certain embodiments, the operations shown in FIG. 4 also generates an object for each header cell that includes a list of headers that may be reviewed to identify label candidates for the header cell. In certain embodiments, one or more such candidates are assigned as a label that is to be associated with the name contained in the header cell. In certain embodiments, the assigned labels are included in data cell objects having a formatted data structure that may be easily consumed by search engines, QA systems, etc.

In certain embodiments, it is assumed that each table cell is already empty or labeled as either a header or data. In certain embodiments, the header label assignment system may make a single pass over the two-dimensional table array and associate each data cell with its appropriate headers. In certain embodiments, values are obtained from the cells in each row and column of the table at operation 405. In certain embodiments, a current list of column headers is maintained. In certain embodiments, a current list of row headers is also maintained.

In certain embodiments, the header label assignment system may include operations to address the presence of embedded headers in a table. To this end, in certain embodiments, the header label assignment system keeps a count of consecutive column headers and, in certain embodiments, a count of consecutive row headers at operation 410. At operation 415, the list of column headers is updated based on the count of consecutive column headers, and the list of row headers is based on the count of consecutive row headers. In certain embodiments, headers from the current list of column headers and current list of row headers are associated with the cell at operation 420. In certain embodiments, when the current list of row headers is associated with the data cell at operation 420, the counts for the consecutive column headers and consecutive row headers are reset. In certain embodiments, the operations shown in FIG. 4 are continued until all data cells of the table have been associated with one or more headers. The resulting data structure in which each data cell is associated with at least one header may be stored for subsequent ingestion and use by, for example, a QA system and/or search engine.

In certain embodiments, the context of one or more of the data cells may be enhanced using label headers. In certain embodiments, label headers may be identified using the header list associated with a header cell. In certain embodiments, label candidates are identified from the header list of each header cell at operation 425. Once the label candidates have been identified, certain embodiments associate headers in a data cell with one or more labels from the identified label candidates at operation 430.

FIG. 5 is another flowchart depicting exemplary operations that may be executed in certain embodiments of the header label assignment system. In certain embodiments, the header label assignment system initializes empty header arrays at operation 502. In certain embodiments, the header label assignment system initializes an empty column header array for each column of the table. In certain embodiments, the header label assignment system also initializes an empty row header array that is used as each column of a row is traversed. In certain embodiments, the header label assignment system initializes an empty label candidate header array to be used to store headers associated with each header cell encountered in the table.

In certain embodiments, the initialization operations executed at operation 502 include the initialization of certain counters. In certain embodiments, consecutive header counters are initialized including a consecutive row header counter, CRHC for the indexed row being traversed by the table and a consecutive column header counter for each column index CCHC(i), where (i) corresponds to the column number of the cell in the table.

In the example of FIG. 5, the initial row and column indices of the cell at which the header label assignment system is to begin processing the table is set at operation 504. In certain embodiments, both the initial row index and initial column index are set to 1 so that processing begins at the first cell of the table indexed at R1C1. In certain embodiments, the header label assignment system may be configured to analyze only a sub-table included in a data set, in which case the row and column indices may be initialized to point to the first cell of the sub-table.

In certain embodiments, the initial row index and initial column index are used to retrieve a cell at the indexed row and column positions within the table at operation 506. At operation 508, a determination is made as to whether the cell at the indexed row and column position is a header. If the cell at the indexed row and column position is a data cell, processing may proceed to the data cell operations shown in FIG. 6 and described in detail herein. Otherwise, if a determination is made that the cell at the indexed row and column position is a header, the value of the CRHC is incremented at operation 510 and the value of the CCHC(i), for the indexed column is incremented at operation 512.

In certain embodiments, the header label assignment system may execute operations to update the column header array for the indexed column and/or the row header array for the indexed row. Certain embodiments may address the presence of embedded headers in a table by updating the column header array and/or row header array based on one or more of the consecutive header counts CRCH and CCHC(i). In certain embodiments, a determination that a header from the row header array is to be removed is made at operation 514 based on the value of CRCH. In certain embodiments, the header label assignment system determines that a row header from the row header array is to be removed when the length of the row header array is greater than or equal to the value of CRCH. In certain embodiments, if the determination at operation 514 indicates that a row header from the row header array is to be removed, it is removed at operation 516.

In certain embodiments, which header is to be removed from the row header array for the indexed row is dependent on the value of CRCH. In certain embodiments, when the value of CRCH=1, the row header that is removed is the last row header in the current version of the row header array. In certain embodiments, when the value of CRCH=2, the row header that is removed is the second from last row header in the current version of the row header array. In certain embodiments, when the value of CRCH=n, the row header that is removed is the n^(th) from last row header in the current version of the row header array.

In certain embodiments, the header label assignment system proceeds to determine whether a header from the column header array for the indexed column is to be removed at operation 518. In certain embodiments, a determination that a header from the column header array where the indexed column is to be removed is based on the value of CCCH(i) for the indexed column. In certain embodiments, the header label assignment system determines that a header from the column header array is to be removed when the length of the column header array for the indexed column is greater than or equal to the value of CCCH(i). In certain embodiments, if the determination at operation 518 indicates that a column header from the column header array is to be removed, it is removed at operation 520.

In certain embodiments, which header is to be removed from the column header array for the indexed column is dependent on the value of CCCH(i). In certain embodiments, when the value of CCCH(i)=1, the column header that is removed is the last column header in the current version of the column header array. In certain embodiments, when the value of CCCH(i)=2, the column header that is removed is the second from last column header in the current version of the column header array. In certain embodiments, when the value of CCCH(i)=x, the column header that is removed is the x^(th) from last column header in the current version of the column header array.

In certain embodiments, the row header array, indexed column header array are updated with the value of the indexed cell once operations 514-520 have been addressed. To this end, the value of the indexed cell may be appended to the row header array at operation 522 and may be appended to the indexed column header array at operation 524.

At operation 525, the indexed cell is associated with the current column header array for the indexed column and the current row away for the indexed row. In certain embodiments, if the cell is a data cell, the header label assignment system may generate and store a data cell object including headers associated with the data found in the indexed data cell. In certain embodiments, if the cell is a header cell, the header label assignment system may generate and store a header cell object including headers associated with the header name found in the indexed data cell.

In certain embodiments, the columns of each indexed row are sequentially traversed in the header assignment operations before proceeding to an analysis of the columns of the next indexed row. To this end, a determination is made at operation 526 whether the indexed row of the table has additional columns. If so, the column index is incremented at operation 528 and the newly incremented column index and current row index are used to retrieve the corresponding cell value at operation 506. If all of the columns of the indexed row have been analyzed, the header label assignment system may determine whether the table includes more rows that are to be analyzed at operation 530. If more rows are to be analyzed, the row index may be incremented at operation 532; the content of the row array may be reset at operation 534; and the column index may be reset to its initial value at and the CRCH reset at operation 536. In certain embodiments, the row index incremented at operation 532 and the value of the reset column index are used to retrieve the corresponding cell value at operation 506.

FIG. 6 is a flowchart depicting exemplary operations that may be executed when a determination is made that the cell at the indexed row and indexed column retrieved at operation 506 (FIG. 5) is a data cell. In certain embodiments, the value of CRCH for the indexed row is reset at operation 606 and value of CCHC(i) for the indexed column is reset at operation 608 before returning to the operations of FIG. 5.

FIG. 7 is a flowchart depicting exemplary operations that may be used to identify label candidates using header cell objects generated, for example, in the operations shown in FIG. 5. In certain embodiments, the header label assignment system has generated header cell objects for each of the header cells within the table 310. In certain embodiments, each header cell has a corresponding header cell object header(x), where (x) is an index identifying the header cell object. In certain embodiments, each header cell object (x) includes a list of header names numbering (y), where (y) is an index pointing to a header name in the corresponding header cell object (x).

In certain embodiments, each header name in a header object may be initially treated as a potential label candidate. In the operations of FIG. 7, the header label assignment system identifies headers that may actually be a label candidate from the list of header names of each header cell object and, in certain embodiments, associates the labels with corresponding headers in data cells.

In certain embodiments, index pointers for (x) and (y) are generated at operation 705. In certain embodiments, the header label assignment system gets object header (x) at operation 705 and accesses the potential label candidate(y) from object header(x) at operation 710. In certain embodiments, a determination is made at operation 715 as to whether the potential candidate(y) is adjacent a data cell. If the potential candidate(y) is adjacent a data cell, it is removed as a potential candidate from the header(x) object at operation 720. In certain embodiments, a determination is made at operation 725 as to whether the potential candidate(y) has already been used as a header label. If the potential candidate(y) has already been used as a label header, it is removed as a potential candidate from header(x) at operation 730. In certain embodiments, a determination is made at operation 735 as to whether there are more potential candidates in the header(x) object. If there are more potential candidates remaining in the header(x) object, the value for the index(y) pointer is incremented at operation 740 and the corresponding candidate is retrieved at operation 710. In certain embodiments, operations 715-735 are repeated until all potential candidates in the header(x) object have been analyzed.

In certain embodiments, once all of the label candidates have been identified for header(x), a label is assigned to the header cell corresponding to the header(x) object at operation 745. In certain embodiments, the label assigned to the header cell corresponds to the label candidate that is closest to the header cell within the table 310.

In certain embodiments, the header label assignment system iteratively executes the foregoing operations for each header object. To this end, a determination may be made at operation 750 as to whether there are more header objects that are to be analyzed for assignment as a header label. If there are more header objects, the value for index(x) may be incremented at operation 755 and the next header object for analysis is accessed at operation 705.

In certain embodiments, the labels are associated with corresponding headers in the data cell objects at operation 760. In certain embodiments, the header labels for the headers may be stored as one or more objects that are separate from the data cell objects. In such embodiments, header labels are associated with the headers within the data cell object during, for example, execution of a search. In certain embodiments, the data cell objects are themselves updated with labels for corresponding headers. In such embodiments, searches including header labels may be executed on the updated data cell objects.

FIG. 8 shows one example of a data structure 800 that may be generated from the table information shown in FIG. 3 using certain embodiments of the header label assignment system. In the specific example shown in FIG. 8, the header label assignment system has provided a JSON output in which the individual data cells of the table are associated with one or more respective headers and the headers are associated with corresponding labels. In certain embodiments, header label “NYC BOROUGH” has been associated with header names “MANHATTAN” and “BROOKLYN in each data cell. In certain embodiments, the data structure 800 may be used by a QA system or search engine. When the QA system or search engine is asked to answer questions that reference the label “NYC BOROUGH” without reference to specific borough names.

FIG. 9 shows another example of a table 900 including information from which header labels may be extracted to enhance the context of the data cells. In this table, the names “Violation”, “Vehicle”, and “NYC Borough” have been identified by the header label assignment system as header labels. The name “Violation” has been assigned as a label for the headers “Speeding Ticket” and “Parking Ticket.” The name “Vehicle” has been assigned as a label for header names “Car” and “SUV.” The name “NYC Borough” has been assigned as a label header for the header names “Manhattan”, “Brooklyn”, “Queens”, and “Bronx.” In certain embodiments, such label assignments may result in the data cell structures shown in JSON table 905.

FIG. 10 depicts one example of pseudocode 1005 that may be used as a basis to implement certain embodiments of the header label assignment system. In certain embodiments, the header label assignment system executes identifies candidate labels from the header objects using, for example, operations represented by instructions exemplified in pseudocode 1005. In certain embodiments, once the header label assignment system has identified the label candidates, the appropriate label candidates are assigned to the corresponding header using, for example, operations represented by instructions exemplified in in pseudocode 1015.

Although the present invention has been described in detail, it should be understood that various changes, substitutions and alterations can be made hereto without departing from the spirit and scope of the invention as defined by the appended claims. 

What is claimed is:
 1. A computer-implementable method for associating data cells with headers and header labels from tables having one or more header structures, comprising: receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, dynamically updating a current list of column headers; and dynamically updating a current list of row headers; dynamically updating a list of header names for the header cell using the current list of column headers and current list of row headers; upon encountering a data cell, assigning the current list of column and row headers to the data cell; and identifying label candidates for the header cell from the list of header names; assigning one or more label candidates as labels to the header cell; and, if the cell is a header cell, incrementing a count of consecutive column headers for the column containing the cell; comparing the incremented count of consecutive column headers for the column containing the cell with a length of an array holding the current list of column headers for the column containing the cell; and if the length of the array holding the current list of column headers for the column containing the cell is greater than the count of consecutive column headers for the column containing the cell, replacing a preceding column header in the current list of column headers containing the cell with a value of the header cell, wherein the header replaced in the current list of column headers is the x^(th) from last header of the current list of column headers, where x is equal to the value of the count of consecutive column headers.
 2. The method of claim 1, wherein identifying label candidates for the header cell from the list of header names comprises: removing a header name as a label candidate from the list of header names if the header name is already used as a label.
 3. The method of claim 1, wherein identifying label candidates for the header cell from the list of header names comprises: assigning a label to the header cell using an identified label candidate that is closest to the header cell within the table.
 4. The method of claim 1, further comprising: if the cell is a header cell, incrementing a count of consecutive row headers for the row containing the cell; comparing the incremented count of consecutive row headers for the row containing the cell with a length of an array holding the current list of row headers for the row containing the cell; and if the length of the array holding the current list of row headers for the row containing the cell is greater than the count of consecutive row headers for the row containing the cell, updating the list of row headers for the row containing the cell by replacing a preceding row header in the current list of column headers containing the cell with a name of the header cell, wherein the header replaced in the current list of row headers is the n^(th) from last header of the current list of column headers, where n is equal to the value of the count of consecutive row headers.
 5. The method of claim 1, further comprising: updating a data structure for each data cell with one or more header labels associated with headers assigned to the data cell.
 6. The method of claim 1, further comprising: storing the data structure in electronic memory; electronically receiving a natural language query; extracting from the natural language query, using a natural language processing engine, two or more query words; and searching the stored data structure for a data structure containing a label that matches the two or more query words, and returning the cell data stored in the data structure as a question answer.
 7. A system comprising: a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, dynamically updating a current list of column headers; and dynamically updating a current list of row headers; dynamically updating a list of header names for the header cell using the current list of column headers and current list of row headers; upon encountering a data cell, assigning the current list of column and row headers to the data cell; and identifying label candidates for the header cell from the list of header names; assigning one or more label candidates as labels to the header cell; and, if the cell is a header cell, incrementing a count of consecutive column headers for the column containing the cell; comparing the incremented count of consecutive column headers for the column containing the cell with a length of an array holding the current list of column headers for the column containing the cell; and if the length of the array holding the current list of column headers for the column containing the cell is greater than the count of consecutive column headers for the column containing the cell, replacing a preceding column header in the current list of column headers containing the cell with a value of the header cell, wherein the header replaced in the current list of column headers is the x^(th) from last header of the current list of column headers, where x is equal to the value of the count of consecutive column headers.
 8. The system of claim 7, wherein identifying label candidates for the header cell from the list of header names comprises: removing a header name as a label candidate from the list of header names if the header name is already used as a label.
 9. The system of claim 7, wherein identifying label candidates for the header cell from the list of header names comprises: assigning a label to the header cell using an identified label candidate that is closest to the header cell within the table.
 10. The system of claim 7, wherein the instructions are further configured for: if the cell is a header cell, incrementing a count of consecutive row headers for the row containing the cell; comparing the incremented count of consecutive row headers for the row containing the cell with a length of an array holding the current list of row headers for the row containing the cell; and if the length of the array holding the current list of row headers for the row containing the cell is greater than the count of consecutive row headers for the row containing the cell, updating the list of row headers for the row containing the cell by replacing a preceding row header in the current list of column headers containing the cell with a name of the header cell, wherein the header replaced in the current list of row headers is the n^(th) from last header of the current list of column headers, where n is equal to the value of the count of consecutive row headers.
 11. The system of claim 7, wherein the instructions are further configured for: updating a data structure for each data cell with one or more header labels associated with headers assigned to the data cell.
 12. The system of claim 7, wherein the instructions are further configured for: storing the data structure in electronic memory; electronically receiving a natural language query; extracting from the natural language query, using a natural language processing engine, two or more query words; and searching the stored data structure for a data structure containing a label that matches the two or more query words, and returning the cell data stored in the data structure as a question answer.
 13. A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with at least one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, dynamically updating a current list of column headers; dynamically updating a current list of row headers; dynamically updating a list of header names for the header cell using the current list of column headers and current list of row headers; upon encountering a data cell, assigning the current list of column and row headers to the data cell; and identifying label candidates for the header cell from the list of header names; assigning one or more label candidates as labels to the header cell and, if the cell is a header cell, incrementing a count of consecutive column headers for the column containing the cell; comparing the incremented count of consecutive column headers for the column containing the cell with a length of an array holding the current list of column headers for the column containing the cell; and if the length of the array holding the current list of column headers for the column containing the cell is greater than the count of consecutive column headers for the column containing the cell, replacing a preceding column header in the current list of column headers containing the cell with a value of the header cell, wherein the header replaced in the current list of column headers is the x^(th) from last header of the current list of column headers, where x is equal to the value of the count of consecutive column headers.
 14. The non-transitory, computer-readable storage medium of claim 13, wherein identifying label candidates for the header cell from the list of header names comprises: removing a header name as a label candidate from the list of header names if the header name is already used as a label; and assigning a label to the header cell using an identified label candidate that is closest to the header cell within the table.
 15. The non-transitory, computer-readable storage medium of claim 13, wherein the instructions are further configured for: if the cell is a header cell, incrementing a count of consecutive row headers for the row containing the cell; comparing the incremented count of consecutive row headers for the row containing the cell with a length of an array holding the current list of row headers for the row containing the cell; and if the length of the array holding the current list of row headers for the row containing the cell is greater than the count of consecutive row headers for the row containing the cell, updating the list of row headers for the row containing the cell by replacing a preceding row header in the current list of column headers containing the cell with a name of the header cell, wherein the header replaced in the current list of row headers is the n^(th) from last header of the current list of column headers, where n is equal to the value of the count of consecutive row headers.
 16. The non-transitory, computer-readable storage medium of claim 13, wherein the instructions are further configured for: updating a data structure for each data cell with one or more header labels associated with headers assigned to the data cell.
 17. The non-transitory, computer-readable storage medium of claim 13, wherein the instructions are further configured for: storing the data structure in electronic memory; electronically receiving a natural language query; extracting from the natural language query, using a natural language processing engine, two or more query words; and searching the stored data structure for a data structure containing a label that matches the two or more query words, and returning the cell data stored in the data structure as a question answer; receiving a table having rows and columns, wherein the table includes a plurality of cells, wherein each cell is populated with one of a header name, data value, or no information; determining whether a cell is a header cell or data cell; if the cell is a header cell, maintaining a count of consecutive column headers; dynamically updating a current list of column headers based on the count of the consecutive column headers; and upon encountering a data cell, assigning the current list of column headers to the data cell. 